Automated branding of generic applications

ABSTRACT

A mobile phone comprising a processor, a memory comprising a system partition and a data partition, and an application stored in the system partition of the memory. When executed by the processor, the application determines a brand identity associated with the mobile phone, accesses branding assets associated with the application based on the brand identity, and adapts the function of the application based on the accessed branding assets.

CROSS-REFERENCE TO RELATED APPLICATIONS

None.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

Electronic devices may be manufactured in a substantially similarhardware and software platform and distinguished based on brandinginformation associated with the devices. For example, a battery coverfeaturing a Brand X logo may be attached to a first electronic device,and a battery cover featuring a Brand Y logo may be attached to a secondelectronic device. The first and second electronic devices may havesubstantially the same hardware and software and be distinguished onlyby the different brand logos on their battery covers. The brandingdistinctions may extend further to include distinct branded splashscreens that display when applications execute on the electronicdevices, to include distinct audio cues that sound when events occur onthe electronic devices, and to include other branding differences. Thebranding of electronic devices may be performed as part of themanufacturing process. In this case, electronic devices that sharecommon hardware and software but that are manufactured as differentbrands are likely to be associated with different stock keeping unit(SKU) identities and may require to be tested separately.

Mobile virtual network operators (MVNOs) are businesses that may leasemobile communication services from wireless communication carriers.Thus, mobile virtual network operators may not own cellular towers,mobile switching centers (MSCs), gateways, and other communicationsinfrastructure but instead may pay fees to the owners of thiscommunication infrastructure to carry the communications traffic oftheir subscribers. The mobile virtual network operators may wish thattheir subscribers use mobile phones that feature their branding ratherthan the branding of the owner of the communications infrastructure,whereby to own and control the subscriber relationship. At the sametime, some mobile virtual network operators may be associated with asmall number of subscribers, at least initially, and may have difficultynegotiating with mobile phone manufacturers to make a small run ofmobile phones manufactured to feature branding associated with theirbusiness.

SUMMARY

In an embodiment, a mobile phone is disclosed. The mobile phonecomprises a processor, a memory comprising a system partition and a datapartition, and an application stored in the system partition of thememory. When executed by the processor, the application determines abrand identity associated with the mobile phone, accesses brandingassets associated with the application based on the brand identity, andadapts the function of the application based on the accessed brandingassets.

In an embodiment, an electronic device is disclosed. The electronicdevice comprises a processor, a memory, and an application stored in thememory. When executed by the processor, the application determines afirst brand identity associated with the electronic device at a firsttime, accesses a plurality of first branding assets associated with theapplication based on the first brand identity, and adapts the functionof the application based on the accessed plurality of first brandingassets, whereby the application provides a first branded userexperience. The application further determines a second brand identityassociated with the electronic device at a second time, accesses aplurality of second branding assets associated with the applicationbased on the second brand identity, and adapts the function of theapplication based on the accessed plurality of second branding assets,whereby the application provides a second branded user experience,wherein the first branded user experience is different from the secondbranded user experience.

In an embodiment, an electronic device is disclosed. The electronicdevice comprises a processor, a memory, and an application stored in thememory. When executed by the processor, the application determines abrand identity associated with the mobile phone, accesses subscriberprofile information, where the profile information comprises at leastone of a sex of the subscriber, an age of the subscriber, a city of thesubscriber, an education level of the subscriber, an income level of thesubscriber, a sports team affiliation of the subscriber, and a personalinterest of the subscriber, accesses branding assets associated with theapplication based on the brand identity and based on the subscriberprofile information, and adapts the function of the application based onthe accessed branding assets.

These and other features will be more clearly understood from thefollowing detailed description taken in conjunction with theaccompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure, referenceis now made to the following brief description, taken in connection withthe accompanying drawings and detailed description, wherein likereference numerals represent like parts.

FIG. 1 is an illustration of a branding system according to anembodiment of the disclosure.

FIG. 2 is a flow chart of a method according to an embodiment of thedisclosure.

FIG. 3 is an illustration of a mobile phone according to an embodimentof the disclosure.

FIG. 4 is a block diagram of a mobile phone according to an embodimentof the disclosure.

FIG. 5A is a block diagram of a software architecture for an electronicdevice according to an embodiment of the disclosure.

FIG. 5B is a block diagram of another software architecture for anelectronic device according to an embodiment of the disclosure.

FIG. 6 is a block diagram of a computer system according to anembodiment of the disclosure.

DETAILED DESCRIPTION

It should be understood at the outset that although illustrativeimplementations of one or more embodiments are illustrated below, thedisclosed systems and methods may be implemented using any number oftechniques, whether currently known or not yet in existence. Thedisclosure should in no way be limited to the illustrativeimplementations, drawings, and techniques illustrated below, but may bemodified within the scope of the appended claims along with their fullscope of equivalents.

In one embodiment, an electronic device that is provided in an initialstate with an initially unbranded generic application is taught. Theinitially unbranded generic application may be a web browserapplication, an electronic mail application, a calendar application, adialer application, a visual voice mail application, or otherapplication. The initially unbranded generic application works with aplurality of different brands, automatically determines a brandassociated with the device, and then adapts itself to provide a brandedexperience to a user of the electronic device when the subject genericapplication executes. For example, the generic application may determineits brand identity, select pre-loaded branding assets that areassociated with the subject brand identity, and configure itself topresent a splash screen defined in the selected pre-loaded brandingassets, to receive a real simple syndication (RSS) feed from a sourcedefined by the selected pre-loaded branding assets, and to employ acolor scheme of its user interface that is defined by the selectedpre-loaded branding assets.

In another embodiment, the electronic device may be provided in aninitial state with an initially branded generic application where thegeneric application can be rebranded using the same mechanisms taught bythe present disclosure. The electronic device may be rebranded, forexample, when a user migrates the electronic device from a firstwireless communication service provider to a different wirelesscommunication service provider. The electronic device may be rebranded,in another example, when a wireless service provider repurposes aplurality of electronic devices initially designated for use with afirst brand to instead be used with a second brand.

By ordering electronic devices in an initially unbranded state and thencausing the devices to change to a variety of different brands afterreceipt of the electronic devices from the manufacturer, a provider ofthe devices may be able to realize a variety of economic benefits. Byordering a large number of generic devices, the provider may be able tonegotiate a lower price on the generic devices due to volume discounts.The price for a lot of 100,000 devices may be less than the summed pricefor buying five different lots of 20,000 devices each, due to volumediscounts offered by the original equipment manufacturer (OEM).Additionally, device testing efficiencies may be realized. For example,it may be less expensive to test the unbranded electronic devices oncethan to test each of the five branded electronic devices once (whichamounts to five different test runs). This efficiency may extend to thetesting of patches and/or software updates provided though the servicelife of the electronic devices. Some applications and branded contentmay be specific and exclusive to particular brands. The genericapplications referred to above, however, are applications that typicallyfind a use under all branded variants of the electronic device. Avariety of approaches to delivering the functionality of theseapplications under different brands can be enumerated. One approach isto deliver a generic application devoid of any branding information.Typically brand sponsors may feel this neglects a valuable opportunityfor them to obtain the marketing advantages associated with branding andhence may reject this approach. Another approach is to deliver adifferent unique application containing the branding information foreach different branded variation of the electronic device. This solutionmay be acceptable to brand sponsors but is complicated, may requireextra labor to be provided by highly skilled and expensive personnel toload the subject branded applications onto the electronic device, andmay entail additional development work to create the different brandedapplications, all of which lead to higher costs that are absorbed by thesupplier and/or by the brand sponsor. The solution taught by the presentdisclosure is a hybrid approach. The generic application may be composedof a plurality of generic assets as well as a plurality of brandingassets that are identified and/or referenced after completion of themanufacturing process.

In an embodiment, the branding assets may be stored along with thegeneric application in a protected memory region that is notconveniently accessible to the ordinary user. For example, the brandingassets may be stored in a system partition of the memory. Alternatively,the branding assets may be stored in a carrier memory partition that isseparate from system memory and separate from data memory.Alternatively, some of the branding assets may be stored in andretrieved by the electronic device from a data store accessible via awireless communication link into a network to which the data store iscoupled.

In an embodiment, when the generic application executes, it maydetermine its brand identity and use this brand identity to configureitself, to select content such as splash screens, wallpaper, background,user interface styles, settings, locations or references to initializereal simple syndication (RSS) feeds, and other. This may be done eachtime the generic application executes. Alternatively, in an embodiment,the generic application may execute branding once and set a brandingflag. When the branding flag is set, the generic application does notexecute branding when initializing. If rebranding is desired, forexample when a subscriber changes carrier and/or brand of communicationsservice, the branding flag may be reset, thus when the genericapplication next initializes it goes through the branding procedure, inthis case associating the generic application with the new branding.

For further discussion of branding generic devices see U.S. patentapplication Ser. No. 12/962,620, filed Dec. 7, 2010, entitled “Systemand Method of Wireless Communication,” by Urbanek and U.S. patentapplication Ser. No. 13/149,505, filed May 31, 2011, entitled “LoadingBranded Media Outside System Partition” by Delker, both of which arehereby incorporated by reference in their entirety. By contrast with thepresent disclosure, U.S. patent application Ser. No. 12/962,620 teachesidentifying applications that are not used by all versions of a genericelectronic device, pre-loading these applications as firmware in thegeneric electronic device as dormant firmware, and selectively enablingthe appropriate applications at a later time when branding the initiallyunbranded generic electronic device. U.S. patent application Ser. No.13/149,505 teaches loading brand-specific files to a non-systempartition memory area of the generic device that were not pre-loaded,whereby to provide some of the branding content such as electronicrepresentations of logos, ring tones, applications, customized controlsand switches. The brand-specific files may be loaded from a removablememory card inserted into a slot of the generic device during branding.While the teachings of U.S. patent application Ser. No. 12/962,620 andof U.S. patent application Ser. No. 13/149,505 may be considered to becomplementary to the teachings of the present disclosure in some ways,the teachings of the present disclosure do not depend on the genericdevice embodying the teachings of U.S. patent application Ser. No.12/962,620 or of U.S. patent application Ser. No. 13/149,505.

Turning now to FIG. 1, a system 100 is described. In an embodiment, thesystem 100 comprises an electronic device 102. The electronic device 102may be adaptable to branding to any of a plurality of different brands.For example, after manufacturing, the electronic device 102 may bebranded to Brand X, to Brand Y, or to some other brand. The process ofbranding the electronic device 102 may include attaching a battery coverto the electronic device 102 having a brand specific logo or othergraphic element. The process of branding may further include loadingbrand specific applications, brand specific content, brand specificsettings, or other branding information based on a brand identity intothe electronic device 102. In an embodiment, the electronic device 102may be a mobile phone, a personal digital assistant (PDA), or a mediaplayer. Alternatively, the electronic device 102 may be a desktopcomputer, a laptop computer, a notebook computer, or other personalcomputing device.

The electronic device 102 comprises a processor 106 and a memory 108. Inan embodiment, the memory 108 may comprise a system partition 110, acarrier partition 112, and a data partition 114. In some embodiments,however, the memory 108 does not have a carrier partition 112. The datapartition 114 may be accessed by applications and/or functionalities ofthe electronic device 102 and may be altered and/or accessed by a userof the electronic device 102. For example, a user of the electronicdevice 102 may change information in the data partition 114 when addingentries to a contacts data store facility of the electronic device 102or when adding a personal note using a note making facility of theelectronic device 102. As another example, the user of the electronicdevice 102 may download and install applications purchased from anon-line store into the data partition 114. In some contexts the systempartition 110 may be referred to as a protected partition, a protectedregion, or the like.

Generally, an ordinary user of the electronic device 102 cannotconveniently change the information in the system partition 110 bydirect interaction. Applications may be placed in the system partition110 to reduce the opportunity for users to corrupt complicated,sophisticated applications, for example web browser applications, phonedialer applications, electronic mail applications, and the like. Withreference to such applications, the ability of users of the electronicdevice 102 to configure the applications may preferably be mediatedthrough controls provided by the applications themselves, where thesecontrols may limit the level of interaction of the user with the systempartition 110, thereby preventing the user from disabling the functionof the subject application or some other application of the electronicdevice 102.

One or more generic applications 120 may be stored in the systempartition 110. As used herein, a generic application 120 ischaracterized as an application whose base function is expected to beused on the electronic device 102 no matter what brand identity isapplied to the electronic device 102. Alternatively, a genericapplication 120 may be an application whose base function may not beused by one or two branded variations of the electronic device 102, butis expected to be used by a plurality of branded variations of theelectronic device 102. A web browser application, for example, may beexpected to be used by the electronic device 102 when branded to aplurality of different branded variations. Other examples of genericapplications 120 are an electronic mail application, a calendarapplication, a dialer application, and a contacts data storeapplication. It is understood that some brand owners may wish tocustomize and/or brand one or more of these generic applications 120,but notwithstanding the base function of the subject genericapplications 120 may remain the same. The base function of a browsergeneric application will be to access and present hypertext markuplanguage (HTML) content based on universal reference locators (URLs) orother links, notwithstanding that it is branded for Brand X or for BrandY. The base function of an email generic application will be to send andreceive electronic mail messages, notwithstanding that it is branded forBrand X or for Brand Y.

In an embodiment, the generic application 120 may be composed of genericcomponents and of branding assets 122. The generic components and/orfirmware may deliver the common and/or base functionality of the genericapplication 120. As illustrated in FIG. 1, these generic components maybe considered to be included in the application 120 block. The brandingassets 122 may provide a branded splash screen, one or more brandedaudio tones, one or more branded settings to apply to the genericapplication 120, one or more brand specific links such as a link to areal simple syndication (RSS) feed address, a link to an on-line storeaffiliated with the brand, executable instructions for brand specificfunctionality, and other brand specific information. The branding assets122 are understood to comprise different sets of branding assets. Forexample, the branding assets 122 may comprise a first set of brandingassets 122 defined by Brand X for branding the generic application 120;a second set of branding assets 122 defined by Brand Y for branding thegeneric application 120; and additional sets of branding assets 122defined by other brands for branding the generic application 120 fortheir specific brands.

When the generic application 120 executes, for example the first timethe generic application 120 is invoked, the generic components maydetermine a brand identity of the electronic device 102 and based on thebrand identity select from the branding assets 122 to brand the genericapplication 120. The brand identity may have been defined for theelectronic device 102 as a provisioning step after completion of themanufacturing process but before the user takes the electronic device102 home from a retail store or receives the electronic device 102 in adelivery to their home. Alternatively, the brand identity may beprovided over-the-air when the electronic device 102 is powered oninitially. Alternatively, the brand identity may be determinedautomatically by the electronic device 102 by analyzing a network accessidentity (NAI) or other identity or security token associated with theelectronic device 102. Alternatively, the brand identity may betransmitted to the electronic device 102 in a message from a wirelessnetwork, for example embedded in a brand identity parameter in an openmobile alliance (OMA) message. In an embodiment, this process ofbranding may occur every time the generic application 120 is activatedand/or loaded for execution. Alternatively, the branding process mayoccur one time, a branding flag may be toggled to indicate that brandinghas been completed, and thereafter the association of the brandingassets 122 associated with the brand identity of the electronic device102 is maintained.

Some of the branding information that may be involved in branding thegeneric application 120 may be accessed via a communication network. Inan embodiment, the electronic device 102 may establish a communicationlink between a radio transceiver 128 of the electronic device 102 and abase transceiver station 130. The base transceiver station 130 maycouple the electronic device 102 to a network 132. The network 132 maycomprise any combination of private networks and public networks. Aserver computer 134 may be connected to the network 132 and therebyaccessible to the electronic device 102. The server 134 provides accessto remotely stored branding assets 138 stored in a data store 136.

In an embodiment, the functionality of the generic application 120accessing some of the remotely stored branding assets 138 via thenetwork 132 may promote a brand owner updating their branding assetsconveniently. In an embodiment, the brand owner may be able to push amessage to the electronic device 102 that causes the generic application120 to complete the branding process, thereby acquiring updated brandinginformation in the remotely stored branding assets 138. Alternatively,the brand owner may be able to push a message to the electronic device102 that causes the generic application 120 to complete a partialbranding process that is restricted to retrieving updated brandingassets 138 via the network 132.

In an embodiment, the generic application 120 may further customizeitself based on a profile associated with the user of the electronicdevice 102. For example, the generic application 120 may access a userprofile and/or subscriber profile stored in the memory 108 oralternatively access the user profile from a profile data store (notshown) via the network 132 and the base transceiver station 130. Basedon the profile information, the generic application 120 may accessbranding assets 122 and/or remotely stored branding assets 138 thatdefine a color scheme, a wallpaper, an aural cue, or other aspectsassociated with the generic application 120. These adaptations mayinvolve adapting the presentation screen provided by the genericapplication. These adaptations may include selecting a real simplesyndication (RSS) feed to activate based on the profile information. Thegeneric application 120 may disable access to the user to the genericapplication 120 based on either the profile information or based on thebrand identity. For example, the generic application 120 may make itsinvocation icon invisible and/or non-responsive to user selection. Thesubscriber profile and/or user profile may include information such as asex of the subscriber, an age of the subscriber, a city of thesubscriber, an education level of the subscriber, an income level of thesubscriber, a sports team affiliation of the subscriber, and a personalinterest of the subscriber.

Turning now to FIG. 2, a method 200 is described. At block 202, thebranding status of the electronic device is determined. For example, abranding status stored in the memory 108 of the electronic device 102may be read to determine whether the electronic device 102 is alreadybranded or is instead unbranded. It is understood that the brandingstatus may have an unbranded status even when the generic application120 has in fact been previously branded, for example when the brandidentity of the electronic device has been changed. If the brandingstatus indicates that the electronic device 102 is already branded, theprocessing loops back to repeat block 202 iteratively. It is understoodthat the processing of method 200 and hence the repetition of block 202may occur on some periodic basis so as to not waste processing capacityof the processor 106. Alternatively, the processing of method 200 mayoccur as a low priority task and hence not delay processing of higherpriority tasks. In an embodiment, the processing of block 202 may beomitted and processing may invariably proceed directly to block 204. Inthis case, the processing of method 200 may occur only occasionally, forexample on initialization of the generic application 120 or on boot-upof the electronic device 102 during power-on.

At block 204, a brand identity of the electronic device is determined.The brand identity may be stored in the memory 108. The brand identitymay be stored in the memory during initial provisioning of theelectronic device 102. Alternatively, the brand identity may be storedin the memory during an open mobile alliance (OMA) communication sessionof the electronic device 102. For example, the electronic device 102 maylearn the brand identity from a brand identity parameter provided in anopen mobile alliance message wireless received by the electronic device102. Alternatively, the brand identity may be determined by analyzing anetwork access identity (NAI) of the electronic device and/or byanalyzing other identifiers and/or security tokens associated with theelectronic device 102. It is understood that the processing of blocks202 and 204 may be performed once by the electronic device 102 and theresults of this processing may be shared by a plurality of genericapplications 120.

At block 206, the generic application 120 is associated with pre-loadedbranding assets 122. The generic application 120 uses the brand identitydetermined in processing block 204 to select a set of branding assets122 from among a plurality of sets of branding assets 122 stored in thesystem partition 110 and/or stored in the carrier partition 112. In anembodiment, the generic application 120 may copy the selected brandingassets 122 into a memory space used by the generic application 120 whenexecuting. Alternatively, the generic application 120 may update indicesor references in the generic application 120 that point to or otherwiseidentify the branding assets 122 that will be used by the genericapplication 120 as it executes. For example, when the genericapplication 120 initializes, it may follow a reference to a brandedsplash screen branding asset 122 to fetch and present graphic content ona display of the electronic device 102.

At block 208, the generic application 120 may optionally retrieveremotely stored branding assets, for example remotely stored brandingassets 138, based on the brand identity determined in block 204. Thebranding assets 122 may include an address or a link to the servercomputer 134 and/or to the remotely stored branding assets 138. At block210, the generic application 120 is associated to the remotely storedbranding assets 138. As above in block 206, the generic application 120may associate to the selected remotely stored branding assets 138 in anumber of different ways. The selected remotely stored branding assets138 may be copied into a memory space associated with the genericapplication 120. Alternatively, references in the generic application120 to branding assets may be updated to reference and/or point to theselected remotely stored branding assets 138.

It is understood that the processing of blocks 206, 208, and 210 may beperformed for each of a plurality of different branded applications 120.For example, the processing of blocks 202 and 204 may be performed once.Thereafter the processing of blocks 206, 208, and 210 may be performedby a generic browser application. Then the processing of blocks 206,208, and 210 may be performed by a generic electronic mail application.Then the processing of blocks 206, 208, and 210 may be performed by ageneric calendar application.

FIG. 3 shows a mobile device 400. FIG. 3 depicts the mobile device 400,which is operable for implementing aspects of the present disclosure,but the present disclosure should not be limited to theseimplementations. Though illustrated as a mobile phone, the mobile device400 may take various forms including a wireless handset, a pager, apersonal digital assistant (PDA), a gaming device, or a media player.The mobile device 400 includes a display 402 and a touch-sensitivesurface and/or keys 404 for input by a user. The mobile device 400 maypresent options for the user to select, controls for the user toactuate, and/or cursors or other indicators for the user to direct. Themobile device 400 may further accept data entry from the user, includingnumbers to dial or various parameter values for configuring theoperation of the handset. The mobile device 400 may further execute oneor more software or firmware applications in response to user commands.These applications may configure the mobile device 400 to performvarious customized functions in response to user interaction.Additionally, the mobile device 400 may be programmed and/or configuredover-the-air, for example from a wireless base station, a wirelessaccess point, or a peer mobile device 400. The mobile device 400 mayexecute a web browser application which enables the display 402 to showa web page. The web page may be obtained via wireless communicationswith a base transceiver station, a wireless network access node, a peermobile device 400 or any other wireless communication network or system.

FIG. 4 shows a block diagram of the mobile device 400. While a varietyof known components of handsets are depicted, in an embodiment a subsetof the listed components and/or additional components not listed may beincluded in the mobile device 400. The mobile device 400 includes adigital signal processor (DSP) 502 and a memory 504. As shown, themobile device 400 may further include an antenna and front end unit 506,a radio frequency (RF) transceiver 508, a baseband processing unit 510,a microphone 512, an earpiece speaker 514, a headset port 516, aninput/output interface 518, a removable memory card 520, a universalserial bus (USB) port 522, an infrared port 524, a vibrator 526, akeypad 528, a touch screen liquid crystal display (LCD) with a touchsensitive surface 530, a touch screen/LCD controller 532, a camera 534,a camera controller 536, and a global positioning system (GPS) receiver538. In an embodiment, the mobile device 400 may include another kind ofdisplay that does not provide a touch sensitive screen. In anembodiment, the DSP 502 may communicate directly with the memory 504without passing through the input/output interface 518. Additionally, inan embodiment, the mobile device 400 may comprise other peripheraldevices that provide other functionality.

The DSP 502 or some other form of controller or central processing unitoperates to control the various components of the mobile device 400 inaccordance with embedded software or firmware stored in memory 504 orstored in memory contained within the DSP 502 itself. In addition to theembedded software or firmware, the DSP 502 may execute otherapplications stored in the memory 504 or made available via informationcarrier media such as portable data storage media like the removablememory card 520 or via wired or wireless network communications. Theapplication software may comprise a compiled set of machine-readableinstructions that configure the DSP 502 to provide the desiredfunctionality, or the application software may be high-level softwareinstructions to be processed by an interpreter or compiler to indirectlyconfigure the DSP 502.

The DSP 502 may communicate with a wireless network via the analogbaseband processing unit 510. In some embodiments, the communication mayprovide Internet connectivity, enabling a user to gain access to contenton the Internet and to send and receive e-mail or text messages. Theinput/output interface 518 interconnects the DSP 502 and variousmemories and interfaces. The memory 504 and the removable memory card520 may provide software and data to configure the operation of the DSP502. Among the interfaces may be the USB port 522 and the infrared port524. The USB port 522 may enable the mobile device 400 to function as aperipheral device to exchange information with a personal computer orother computer system. The infrared port 524 and other optional portssuch as a Bluetooth interface or an IEEE 802.11 compliant wirelessinterface may enable the mobile device 400 to communicate wirelesslywith other nearby handsets and/or wireless base stations.

The keypad 528 couples to the DSP 502 via the interface 518 to provideone mechanism for the user to make selections, enter information, andotherwise provide input to the mobile device 400. Another inputmechanism may be the touch screen LCD 530, which may also display textand/or graphics to the user. The touch screen LCD controller 532 couplesthe DSP 502 to the touch screen LCD 530. The GPS receiver 538 is coupledto the DSP 502 to decode global positioning system signals, therebyenabling the mobile device 400 to determine its position.

FIG. 5A illustrates a software environment 602 that may be implementedby the DSP 502. The DSP 502 executes operating system software 604 thatprovides a platform from which the rest of the software operates. Theoperating system software 604 may provide a variety of drivers for thehandset hardware with standardized interfaces that are accessible toapplication software. The operating system software 604 may be coupledto and interact with application management services (AMS) 606 thattransfer control between applications running on the mobile device 400.Also shown in FIG. 5A are a web browser application 608, a media playerapplication 610, JAVA applets 612, and a generic application 614. Theweb browser application 608 may be executed by the mobile device 400 tobrowse content and/or the Internet, for example when the mobile device400 is coupled to a network via a wireless link. The web browserapplication 608 may permit a user to enter information into forms andselect links to retrieve and view web pages. The media playerapplication 610 may be executed by the mobile device 400 to play audioor audiovisual media. The JAVA applets 612 may be executed by the mobiledevice 400 to provide a variety of functionality including games,utilities, and other functionality. The generic application 614 may besubstantially similar to the generic application 120 described above.

FIG. 5B illustrates an alternative software environment 620 that may beimplemented by the DSP 502. The DSP 502 executes operating systemsoftware 628 and an execution runtime 630. The DSP 502 executesapplications 622 that may execute in the execution runtime 630 and mayrely upon services provided by the application framework 624.Applications 622 and the application framework 624 may rely uponfunctionality provided via the libraries 626.

FIG. 6 illustrates a computer system 780 suitable for implementing oneor more embodiments disclosed herein. For example, the server 134described above with reference to FIG. 1 may be implemented as thecomputer system 780 described below. The computer system 780 includes aprocessor 782 (which may be referred to as a central processor unit orCPU) that is in communication with memory devices including secondarystorage 784, read only memory (ROM) 786, random access memory (RAM) 788,input/output (I/O) devices 790, and network connectivity devices 792.The processor 782 may be implemented as one or more CPU chips.

It is understood that by programming and/or loading executableinstructions onto the computer system 780, at least one of the CPU 782,the RAM 788, and the ROM 786 are changed, transforming the computersystem 780 in part into a particular machine or apparatus having thenovel functionality taught by the present disclosure. It is fundamentalto the electrical engineering and software engineering arts thatfunctionality that can be implemented by loading executable softwareinto a computer can be converted to a hardware implementation by wellknown design rules. Decisions between implementing a concept in softwareversus hardware typically hinge on considerations of stability of thedesign and numbers of units to be produced rather than any issuesinvolved in translating from the software domain to the hardware domain.Generally, a design that is still subject to frequent change may bepreferred to be implemented in software, because re-spinning a hardwareimplementation is more expensive than re-spinning a software design.Generally, a design that is stable that will be produced in large volumemay be preferred to be implemented in hardware, for example in anapplication specific integrated circuit (ASIC), because for largeproduction runs the hardware implementation may be less expensive thanthe software implementation. Often a design may be developed and testedin a software form and later transformed, by well known design rules, toan equivalent hardware implementation in an application specificintegrated circuit that hardwires the instructions of the software. Inthe same manner as a machine controlled by a new ASIC is a particularmachine or apparatus, likewise a computer that has been programmedand/or loaded with executable instructions may be viewed as a particularmachine or apparatus.

The secondary storage 784 is typically comprised of one or more diskdrives or tape drives and is used for non-volatile storage of data andas an over-flow data storage device if RAM 788 is not large enough tohold all working data. Secondary storage 784 may be used to storeprograms which are loaded into RAM 788 when such programs are selectedfor execution. The ROM 786 is used to store instructions and perhapsdata which are read during program execution. ROM 786 is a non-volatilememory device which typically has a small memory capacity relative tothe larger memory capacity of secondary storage 784. The RAM 788 is usedto store volatile data and perhaps to store instructions. Access to bothROM 786 and RAM 788 is typically faster than to secondary storage 784.The secondary storage 784, the RAM 788, and/or the ROM 786 may bereferred to in some contexts as computer readable storage media and/ornon-transitory computer readable media.

I/O devices 790 may include printers, video monitors, liquid crystaldisplays (LCDs), touch screen displays, keyboards, keypads, switches,dials, mice, track balls, voice recognizers, card readers, paper tapereaders, or other well-known input devices.

The network connectivity devices 792 may take the form of modems, modembanks, Ethernet cards, universal serial bus (USB) interface cards,serial interfaces, token ring cards, fiber distributed data interface(FDDI) cards, wireless local area network (WLAN) cards, radiotransceiver cards such as code division multiple access (CDMA), globalsystem for mobile communications (GSM), long-term evolution (LTE),worldwide interoperability for microwave access (WiMAX), and/or otherair interface protocol radio transceiver cards, and other well-knownnetwork devices. These network connectivity devices 792 may enable theprocessor 782 to communicate with the Internet or one or more intranets.With such a network connection, it is contemplated that the processor782 might receive information from the network, or might outputinformation to the network in the course of performing theabove-described method steps. Such information, which is oftenrepresented as a sequence of instructions to be executed using processor782, may be received from and outputted to the network, for example, inthe form of a computer data signal embodied in a carrier wave.

Such information, which may include data or instructions to be executedusing processor 782 for example, may be received from and outputted tothe network, for example, in the form of a computer data baseband signalor signal embodied in a carrier wave. The baseband signal or signalembedded in the carrier wave, or other types of signals currently usedor hereafter developed, may be generated according to several methodswell known to one skilled in the art. The baseband signal and/or signalembedded in the carrier wave may be referred to in some contexts as atransitory signal.

The processor 782 executes instructions, codes, computer programs,scripts which it accesses from hard disk, floppy disk, optical disk(these various disk based systems may all be considered secondarystorage 784), ROM 786, RAM 788, or the network connectivity devices 792.While only one processor 782 is shown, multiple processors may bepresent. Thus, while instructions may be discussed as executed by aprocessor, the instructions may be executed simultaneously, serially, orotherwise executed by one or more multiple processors. Instructions,codes, computer programs, scripts, and/or data that may be accessed fromthe secondary storage 784, for example, hard drives, floppy disks,optical disks, and/or other device, the ROM 786, and/or the RAM 788 maybe referred to in some contexts as non-transitory instructions and/ornon-transitory information.

In an embodiment, the computer system 780 may comprise two or morecomputers in communication with each other that collaborate to perform atask. For example, but not by way of limitation, an application may bepartitioned in such a way as to permit concurrent and/or parallelprocessing of the instructions of the application. Alternatively, thedata processed by the application may be partitioned in such a way as topermit concurrent and/or parallel processing of different portions of adata set by the two or more computers. In an embodiment, virtualizationsoftware may be employed by the computer system 780 to provide thefunctionality of a number of servers that is not directly bound to thenumber of computers in the computer system 780. For example,virtualization software may provide twenty virtual servers on fourphysical computers. In an embodiment, the functionality disclosed abovemay be provided by executing the application and/or applications in acloud computing environment. Cloud computing may comprise providingcomputing services via a network connection using dynamically scalablecomputing resources. Cloud computing may be supported, at least in part,by virtualization software. A cloud computing environment may beestablished by an enterprise and/or may be hired on an as-needed basisfrom a third party provider. Some cloud computing environments maycomprise cloud computing resources owned and operated by the enterpriseas well as cloud computing resources hired and/or leased from a thirdparty provider.

In an embodiment, some or all of the functionality disclosed above maybe provided as a computer program product. The computer program productmay comprise one or more computer readable storage medium havingcomputer usable program code embodied therein to implement thefunctionality disclosed above. The computer program product may comprisedata structures, executable instructions, and other computer usableprogram code. The computer program product may be embodied in removablecomputer storage media and/or non-removable computer storage media. Theremovable computer readable storage medium may comprise, withoutlimitation, a paper tape, a magnetic tape, a magnetic disk, an opticaldisk, a solid state memory chip, for example analog magnetic tape,compact disk read only memory (CD-ROM) disks, floppy disks, jump drives,digital cards, multimedia cards, and others. The computer programproduct may be suitable for loading, by the computer system 780, atleast portions of the contents of the computer program product to thesecondary storage 784, to the ROM 786, to the RAM 788, and/or to othernon-volatile memory and volatile memory of the computer system 780. Theprocessor 782 may process the executable instructions and/or datastructures in part by directly accessing the computer program product,for example by reading from a CD-ROM disk inserted into a disk driveperipheral of the computer system 780. Alternatively, the processor 782may process the executable instructions and/or data structures byremotely accessing the computer program product, for example bydownloading the executable instructions and/or data structures from aremote server through the network connectivity devices 792. The computerprogram product may comprise instructions that promote the loadingand/or copying of data, data structures, files, and/or executableinstructions to the secondary storage 784, to the ROM 786, to the RAM788, and/or to other non-volatile memory and volatile memory of thecomputer system 780.

In some contexts, the secondary storage 784, the ROM 786, and the RAM788 may be referred to as a non-transitory computer readable medium or acomputer readable storage media. A dynamic RAM embodiment of the RAM788, likewise, may be referred to as a non-transitory computer readablemedium in that while the dynamic RAM receives electrical power and isoperated in accordance with its design, for example during a period oftime during which the computer 780 is turned on and operational, thedynamic RAM stores information that is written to it. Similarly, theprocessor 782 may comprise an internal RAM, an internal ROM, a cachememory, and/or other internal non-transitory storage blocks, sections,or components that may be referred to in some contexts as non-transitorycomputer readable media or computer readable storage media.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods may beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein. For example, the variouselements or components may be combined or integrated in another systemor certain features may be omitted or not implemented.

Also, techniques, systems, subsystems, and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as directly coupled or communicating witheach other may be indirectly coupled or communicating through someinterface, device, or intermediate component, whether electrically,mechanically, or otherwise. Other examples of changes, substitutions,and alterations are ascertainable by one skilled in the art and could bemade without departing from the spirit and scope disclosed herein.

What is claimed is:
 1. A mobile phone, comprising: a processor; a memorycomprising a system partition and a data partition; and a genericapplication stored in the system partition of the memory that, whenexecuted by the processor, determines a branding status of the mobilephone, wherein the branding status is initially set to an unbrandedstatus; determines a brand identity associated with the mobile phone,wherein the generic application determines the brand identity at leastin part based on a network access identity (NAI) associated with themobile phone, accesses branding assets associated with the genericapplication based on the brand identity, wherein the branding assets areaccessed from a plurality of pre-loaded branding assets stored in thememory, and wherein the branding assets comprise two or more of a splashscreen, a wallpaper, a background, a user interface style, a colorscheme, an aural cue, an icon, or a real simple syndication (RSS)address, adapts a presentation screen of the mobile phone based on theaccessed branding assets, and updates the branding status of the mobilephone to a branded status based on the brand identity, wherein the basefunctionality of the generic application remains the same in both theunbranded status and the branded status, and wherein the mobile phone isupdated from the unbranded status to the branded status withoutre-provisioning the generic application.
 2. The mobile phone of claim 1,wherein the generic application determines the brand identity at leastin part based on a brand identity parameter provided in an open mobilealliance (OMA) message wirelessly received by the mobile phone.
 3. Themobile phone of claim 1, wherein the generic application is one of a webbrowser application, a phone dialer application, a calendar application,an electronic mail application, and a voice mail application.
 4. Themobile phone of claim 1, wherein the branding assets are stored in thedata partition of the memory.
 5. An electronic device, comprising: aprocessor; a memory; and a generic application stored in the memorythat, when executed by the processor, determines a first brand identityassociated with the electronic device at a first time, accesses aplurality of first branding assets associated with the genericapplication based on the first brand identity, wherein the plurality offirst branding assets are stored in the memory, adapts a presentationscreen of the electronic device based on the accessed plurality of firstbranding assets, whereby the generic application provides a firstbranded user experience, determines a second brand identity associatedwith the electronic device at a second time, wherein the genericapplication determines the second brand identity based on at least oneof a network access identity (NAI) associated with the mobile phone or abrand identity parameter provided in a wirelessly received message froma wireless network, accesses a plurality of second branding assetsassociated with the generic application based on the second brandidentity, wherein the plurality of second branding assets are stored inthe memory, and adapts the presentation screen of the electronic devicebased on the accessed plurality of second branding assets, whereby thegeneric application provides a second branded user experience, whereinthe first branded user experience is different from the second brandeduser experience, wherein the base functionality of electronic deviceremains the same for both the first brand identity and the second brandidentity, and wherein the electronic device adapts from the first brandidentity to the second brand identity without re-provisioning thegeneric application.
 6. The electronic device of claim 5, wherein theelectronic device is manufactured as an unbranded electronic device andwherein the first brand identity is associated with the electronicdevice after the manufacturing process has completed.
 7. The electronicdevice of claim 5, wherein the electronic device is one of a mobilephone, a personal digital assistant (PDA), and a media player.
 8. Theelectronic device of claim 5, wherein the first plurality of brandingassets and the second plurality of branding assets are pre-loaded in thememory.
 9. The electronic device of claim 5, wherein at least some ofthe second plurality of branding assets are downloaded to the electronicdevice via a wireless communication link.
 10. The electronic device ofclaim 5, wherein one of the first brand identity or the second brandidentity is associated with a mobile virtual network operator (MVNO)brand.
 11. The electronic device of claim 5, wherein the genericapplication is stored in a system partition of the memory and whereinthe first plurality of branding assets are stored in a carrier partitionof the memory.
 12. The electronic device of claim 5, wherein at leastone of the plurality of first branding assets or the plurality of secondbranding assets comprise two or more of a splash screen, a wallpaper, abackground, a user interface style, a color scheme, an aural cue, anicon, or a real simple syndication (RSS) address.
 13. The electronicdevice of claim 5, wherein the generic application determines the secondbrand identity at least in part based on a brand identity parameterprovided in an open mobile alliance (OMA) message wirelessly received bythe mobile phone.
 14. An electronic device, comprising: a processor; amemory; and a generic application stored in the memory that, whenexecuted by the processor, determines a first branding status of theelectronic device, wherein the first branding status comprises at leastone of an unbranded status or a branded status based on a first brandidentity; determines a second brand identity associated with theelectronic device, wherein the generic application determines the secondbrand identity based at least in part based on one of a network accessidentity (NAI) associated with the mobile phone or an open mobilealliance (OMA) message wirelessly received by the mobile phone, accessesa first plurality of branding assets associated with the genericapplication based on the second brand identity, accesses subscriberprofile information, where the subscriber profile information comprisesat least one of a sex of the subscriber, an age of the subscriber, acity of the subscriber, an education level of the subscriber, an incomelevel of the subscriber, a sports team affiliation of the subscriber, ora personal interest of the subscriber, accesses a second plurality ofbranding assets selected from the first plurality of branding assetsassociated with the generic application based on the subscriber profileinformation, adapts a presentation screen of the electronic device usingthe second plurality of branding assets, and updates a branding statusof the electronic device to a second branding status based on the secondbrand identity, wherein the base functionality of electronic deviceremains the same for both the first branding status and the secondbranding status, and wherein the electronic device updates from thefirst branding status to the second branding status withoutre-provisioning the generic application.
 15. The electronic device ofclaim 14, wherein the subscriber profile information is accessed by theelectronic device from a server computer.
 16. The electronic device ofclaim 14, wherein the generic application further adapts the function ofthe generic application by selecting a real simple syndication (RSS)feed to activate.
 17. The electronic device of claim 14, wherein thegeneric application further adapts the function of the genericapplication by disabling access to the generic application.
 18. Theelectronic device of claim 14, wherein the electronic device is a mobilephone.
 19. The electronic device of claim 14, wherein the genericapplication and at least some of the first plurality of branding assetsare stored in a system partition of the memory.
 20. The electronicdevice of claim 14, wherein the second plurality of branding assetscomprise two or more of a splash screen, a wallpaper, a background, auser interface style, a color scheme, an aural cue, an icon, or a realsimple syndication (RSS) address.